1. Findings

During the testing, as usual minor issues were found and fixed. In particular a question arose as to the interpretation of text in the WebDAV ACL spec surrounding what clients need to send in an ACL request. Follow-up discussion is needed on that topic.

The CalDAV specification has been tested quite extensively over the last several interoperability tests. Therefore, recent events had tested either problematic areas or have focused on new portions of the specification such as sync reports.

The newer CardDAV specification also was tested. There is only a small subset of tests for the specification as it is still evolving.

The following outlines findings and observations found during testing:

The WebDAV ACL RFC is not ambiguous on whether protected ACEs should be sent when the ACL HTTP verb is used to change the access control list on a resource. There was discussion on whether or not protected ACEs and inherited ACEs should be sent. If a client doesn’t send inherited ACEs, but sends protected ones, this results in errors reported by the server. This is the area that requires further discussion.

Rountrip of X- properties results in the X- properties being put into NOTE property as a text value.

Some implicit scheduling was tested between normal and calendar users and a resource.

PUTs of events on URIs that don’t have the resource name in the <UID>.ics format result in 302 redirect response.